Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bylaw: VPO Election #22

Open
wants to merge 2 commits into
base: master
Choose a base branch
from
Open

Bylaw: VPO Election #22

wants to merge 2 commits into from

Conversation

jacobjk01
Copy link

@jacobjk01 jacobjk01 commented Aug 4, 2022

Bylaw

Drafted: Elizabeth Wu, Jacob Kim

Proposed: 2022.07.28

Proposed by: Executive Team (Elizabeth Wu, Shannon Bonet, Jacob Kim, Kelly Hu, Jenny Jiang, Anu Thirunarayanan)

Ratified: 2022.08.04

Voting Record

Votes: 5 Total Membership, 5 Yes, 0 No, 0 Abstain

Text

Decision Log Entry

Bylaw proposal allowing for the VPO role election to be held asynchronously and online due to atypical timeline after passing VPO amendment.

Other checklist (remove once completed):

  • Add voting members for review or attach picture of voting record
  • Add person(s) who drafted the proposal as assignees.
    • If it is a feature, add the person who made the feature to assignees
  • Prepend title with the type (i.e. "Amendment:")
  • Add the correct label to the PR
  • The merge commit should include Drafted, Proposed, Proposed By, Ratified, and Voting Record.
  • If change was for a bylaw or amendment, make sure to create a new release after merging into master according to the format specified in the README

CC: @calblueprint/eteam

@jacobjk01 jacobjk01 self-assigned this Aug 4, 2022
Copy link
Member

@shannonbonet shannonbonet left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

looks good

@elixawu elixawu changed the title vpo bylaw Bylaw: VPO Election Aug 5, 2022
Copy link
Member

@elixawu elixawu left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm! do we still have to "create a new release after merging into master according to the format specified in the README"?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants